How It Works
BigQuery Datashare uses Google Cloud’s dataset sharing to replicate Dune’s data into your project:- Cross-Project Sharing: Dune grants your project access to shared datasets containing our blockchain data
- Regional Replication: Data is replicated to your preferred region (US Central 1 or EU West 2)
- Native Integration: Shared datasets appear as regular BigQuery datasets in your project
- Automatic Sync: Fresh data arrives daily/hourly without manual intervention
Get Started
Trial: Email datashares-sales@dune.com or contact enterprise team Requirements:- GCP Project ID
- Preferred region (US Central 1 or EU West 2)
- Chains of interest
Sharing Identifiers
BigQuery uses dataset sharing for accessing Dune data:- Analytics Hub: Shared datasets appear in your project’s Analytics Hub
- Direct sharing: We grant access to specific dataset IDs in your project
Principal Types
We need a “Principal” to grant access. This can be:Type | Format | Example |
---|---|---|
User | user:email@domain.com | user:bob@acme.com |
Service Account | serviceAccount:name@project.iam.gserviceaccount.com | serviceAccount:etl-sa@cust-proj.iam.gserviceaccount.com |
Domain | domain:domain.com | domain:acme.com |
Project Service Accounts | principalSet://cloudresourcemanager.googleapis.com/projects/PROJECT_NUMBER/type/ServiceAccount | All service accounts for project |
Most common: provide your email address or a service account email. We can share complete blockchain history in seconds.
Data Types
BigQuery uses native types for blockchain data:Addresses & Hashes
Large Integers
BigQuery’sBIGNUMERIC
handles uint256/int256 natively:
Event Logs
Query Optimization
- Use
block_time
in WHERE clauses for partitioning - Select only needed columns
- Tables are clustered by common query patterns
Regions
Region | Chains | Freshness |
---|---|---|
US Central 1 | 50+ | 24 hours |
EU West 2 | 50+ | 24 hours |